Method and system for managing software installs in a distributed computer network

ABSTRACT

A method of and system for managing installs to a set of one or more field machines in a distributed network environment. In an illustrative embodiment, the system includes at least one change coordinator server that includes a database with data identifying a current state of each field machine, and a change controller routine for initiating a given control action to initiate an update to the current state on a given field machine. In particular, the change controller routine may include a scheduling algorithm that evaluates data from the database and identifies a set of field machines against which the given control action may be safely executed at a given time. At least one install server is responsive to the change controller routine initiating the given control action for invoking the update to the current state on the given field machine.

BACKGROUND OF THE INVENTION

[0001] 1. Technical Field

[0002] The present invention relates generally to distributed computer networks and the management of such networks.

[0003] 2. Description of the Related Art

[0004] Machines and collections of machines are defined by their state. A significant and complex portion of this state is the configuration that drives the behavior of the components running on those machines and interacting with those machines. A distributed computing environment typically implements techniques that attempt to provide a consistent mechanism for managing and changing both machine states and the configuration of machines and collections of machines.

[0005] A guiding principle is to drive the state and configuration of machines to a desired state. When possible, this should be done in a closed-loop fashion to avoid drift between machines and to maintain consistency across the network. For example, even if a machine misses a software install, the following install should bring it up to a consistent and correct state. Minimizing drift and maintaining consistency and repeatability is important for allowing a network with a large number of machines to be managed reliably and, optimally, preferably without or with minimal human intervention. If machine states are not reasonably consistent and predictable, assuring the quality of changes becomes an impossible task, as there may be a massive number of permutations to defend against.

[0006] Moreover, even when the network is not intentionally being kept in a heterogeneous state, there will always be some heterogeneity. Changes to the network are never atomic. It takes time for installs and configuration updates to propagate across the network. In many cases, this is intentional (when installs and configuration changes are staged) and in other cases it is a result of the need to coordinate changes so that only a portion of the network is undergoing an install at any one time. There are also straggler machines, often due to connectivity problems during an install or due to other install failures. There are other cases where multiple versions of some software are intentionally running on different parts of the network at the same time, sometimes for extended periods of time. Whatever the reason, the software and configuration state of the network can be assumed to be heterogeneous at any point in time. Different machines will not only have different states, they may also have different perceptions of the states of other machines. Having every machine constantly updating its configuration and state to reflect the heterogeneity is a very hard problem. It is desirable to track heterogeneity where necessary, but just as importantly, it is desirable to make sure that everything is robust enough to be tolerant of heterogeneity in cases where fully tracking and responding to it is not possible.

[0007] Consider the need to perform configuration and software installs across a large distributed computer network. In such networks, it is known to use an application deployment utility (e.g. NetDeploy) that involves having humans running a script that makes secure (e.g., SSH) connections to a specified list of machines, copies out a configuration file and an archive of software (e.g., a tarball, an archive of files created with the Unix tar utility), and then invokes a host setup process on the machine to configure and install the software. This means that machines only change states when a human actively runs the install process to change the state of an individual machine or group of machines. Changing the network configuration or deploying new software involves running an install against all of the machines in the network. This is a time-intensive process for a human, and stragglers (machines that miss an install) will continue to run with old software and an old view of the world.

[0008] The present invention addresses these and other associated problems of the prior art.

BRIEF SUMMARY OF THE INVENTION

[0009] It is an object of the invention to provide a new paradigm for the installation of software and configuration data in a distributed computer network.

[0010] It is another object of the invention to provide for improved management of the configuration of a distributed network and the software running on the network.

[0011] A more specific object of the invention it to enable faster software installs in a distributed network, even as the network scales to include more hosts.

[0012] Another object is to provide mechanisms that facilitate rapid and smooth changes to the state of the network.

[0013] A more specific object of the invention is to facilitate effective methods for having a heterogenous network state. These methods enable network administrators to cleanly and slowly roll out new major versions of software components, or to have a different version of a component running in selected machines or groups or machines.

[0014] Yet another object of the invention is to provide better management of the machines targeted for installation, especially to reduce the problems associated with “straggler” machines.

[0015] Still another object of the invention is to provide improved management of network configuration allowing rapid and smooth changes to the state of the network within safety invariants, and increasing the speed and scalability of installs.

[0016] The present invention is a new install paradigm. The new install paradigm still retains the concept of a host setup (which is a mechanism for bringing the state of a machine to a desired state), but the paradigm changes the way in which machines are installed. After a bootstrap install to place a “host install manager” onto a given machine, machines instead pull down information about their desired state. When a machine is in a state different from its desired state (e.g., running with a different configuration file or different software), the machine preferably pulls down anything needed for the transition into the new state and then runs the host setup mechanism. This means that installs will eventually “just happen” and that stragglers will automatically get caught and cleaned up. According to the invention, it is also possible to specify a heterogeneous state for the network, allowing the network administrator to temporarily run different versions of software on different parts of the network.

[0017] In an embodiment, a method of and system for managing installs to a set of one or more field machines in a distributed network environment is described. In this illustrative embodiment, the system includes at least one change coordinator server that includes a database with data identifying a current state of each field machine, and a change controller routine for initiating a given control action to initiate an update to the current state on a given field machine. In particular, the change controller routine may include a scheduling algorithm that evaluates data from the database and identifies a set of field machines against which the given control action may be safely executed at a given time. At least one install server is responsive to the change controller routine initiating the given control action for invoking the update to the current state on the given field machine.

[0018] The foregoing has outlined some of the more pertinent features of the invention. These features should be construed to be merely illustrative. Many other beneficial results can be attained by applying the disclosed invention in a different manner or by modifying the invention as will be described.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019]FIG. 1 is a block diagram of a distributed computing environment in which the software management system of the present invention may be implemented;

[0020]FIG. 2 is a block diagram of the main processing components used in the software management system of the present invention;

[0021]FIG. 3 is a representative operational sequence when the field machine does not require an install;

[0022]FIG. 4 illustrates a representative operational sequence when the field machine does need an install;

[0023]FIG. 5 illustrates a preferred way in which ordinary control of the system is performed;

[0024]FIG. 6 illustrates how new machines (e.g., those not yet running IR) are brought into the management system;

[0025]FIG. 7 illustrates a representative Change Coordinator (CC) component of the software management system of the present invention; and

[0026]FIG. 8 illustrates a representative Installer component of the software management system of the present invention.

DETAILED DESCRIPTION OF AN EMBODIMENT

[0027] As seen in FIG. 1, a distributed computing environment 100 in which the software management system of the invention may be implemented includes a set of field machines 102 that facilitate or provide a given operation, such as Internet content delivery. How a particular field machine is used is not particularly relevant to the present invention, as the invention is directed generally to how software gets installed on that machine remotely, as opposed to the particular function of that software. Generalizing, a field machine 102 is any machine or “host” installable by an application deployment routine (e.g., NetDeploy) and identifiable through information residing in a network configuration file. As seen in FIG. 1, the inventive management system also includes a set of Install Server(s) 104, each of which is a host running an Installer component 106. The management system of the invention also includes a set of Change Coordinator(s) 108, each of which is a host running a Change Coordinator (CC) component 110. Generalizing, the Installer 106 and Change Coordinator 110 components comprise software code (or its equivalent) for carrying out various functions as will be described below.

[0028] The software management system has a basic design that is preferably a two-layered one. A first or “inner” layer consists of the Change Coordinator hosts 108, which hosts are responsible for complex tasks such as maintaining a database of host states, determining which hosts should be installed at what time, and generally forming the core of the system. Preferably, Change Coordinators 108 communicate with Install Servers 104 over a given communications channel, and with clients via HTTPS. The Change Coordinators receive frequent reports about host states via processes that are referred to herein for convenience as an Install Reporter (IR) 112 and an Install Listener (IL) 114. As will be described below, IR typically runs on a field machine 102, and IL typically runs on a CC host 108, although it can run on any field machine 102 as well. Preferably, Change Coordinator hosts communicate with all other Change Coordinators frequently, if not constantly, to keep their databases synchronized.

[0029] The second or “outer” layer consists of the Install Servers 104, which machines may be stateless, existing partially to provide a barrier between the Change Coordinators and the rest of the network. Preferably, Change Coordinators are contacted by field machines, which provide their install status. Alternatively, field machines contact Install Servers with this information, which is then passed on to Change Coordinators. Install Servers are instructed by the Change Coordinators to install field machines, and then perform those installs, typically using application deployment utilities. The Install Servers preferably communicate with Change Coordinators over a given communication channel, and they preferably receive reports from field machines and trigger field installs using an SSH channel.

[0030] As one of ordinary skill in the art will appreciate, this model is essentially “pull-triggered,” as most installs are triggered by an action beginning on the machine being installed.

[0031] As seen in FIG. 2, the system 200 comprises four major process components that have been previously identified: an Install Reporter (IR) 202, an Install Listener (IL) 204, an Installer 206, and a Change Coordinator (CC) 208. IL 204 may be part of CC 208, or a separate component. The IR component 202 is very simple. It is run regularly on field machines. A convenient mechanism for doing this (in a Unix-based environment) is to use a Unix cron, which is a program that enables Unix users to execute commands or scripts automatically at a specified time/date. The IR component 202 reads local disk to determine the release that the host is currently installed with. The IR component 202 then opens a connection (e.g., via UDP) to the hostname that resolves to the set of machines running an Install Listener process (IL) 204. The IR component 202 then transmits its release information (and, perhaps its IP address) over that connection using a convenient protocol.

[0032] The IL component 204 preferably is an always-running server. It can run on any field machine, but this component preferably runs initially on the CC hosts for simplicity. The IL component 204 receives reports from field machines running IR component 202. Communication is preferably one-way, and the IL component 204 is not expected to send any data back to the machine sending data. Data coming in to the IL component 204 is then fed outward to the Installer component 206 running on that machine.

[0033] The Installer 206 is the component whose role is to directly invoke installation of software onto field machines. This component receives data about field machines from the IL component 204. It passes most of this data on to the Change Coordinator system. When directed to do so, the Installer 206 invokes the installation of software onto field machines. In an illustrated embodiment, the machines are servers in a content delivery network (CDN), although this is not a limitation of the present invention, as previously noted.

[0034] The CC component 208 is the primary control mechanism in the system. It maintains a local database with a great deal of information about the known and desired states of field machines. It receives this information from multiple sources including the Install Servers, IL, other distributed data collection systems, and other network configuration files and release definitions. The CC component 208 maintains communications with Installer processes 206 on Install Servers, and it directs them to drive installs at appropriate times. These installs and their timing are determined by rules to maintain stability of the network. The engine for managing these rules is a part of the CC component 208 and will be described below. The CC component 208 may also provide direct human interaction through an appropriate user interface. In particular, it provides an interface that can be used to control the operating parameters of the CC process. Preferably, CC component 208 speaks HTTPS to requesting clients.

[0035]FIG. 3 illustrates a representative operational sequence when the field machine does not require an install. The most frequently occurring sequence of events occurs as follows. A field machine 300 invokes IR (e.g., out of Unix cron), which at step (1) sends its label to an IL machine 302. The identity of the IL machine 302 preferably is determined by looking up a DNS name that resolves to some set of hosts running IL. The particular DNS strategy is not critical. An arbitrary host's IL process receives this report. At step (2), the field machine's IP address and current label are passed along to the Change Coordinator host 304 that the IL host is then talking to at the moment. This Change Coordinator consults its database and determines that the field machine does not currently require an install.

[0036]FIG. 4 illustrates a representative operational sequence when the field machine does need an install. Steps (1)-(2) of FIG. 3 are repeated. Here, however, the Change Coordinator 404 determines what software and configuration the field machine should have and, at step (3) instructs (3) the Installer 408 process running on the Install Server 406 to install the host to match that data. The Installer 408 queues the install and, at step (4), installs the field machine 400. Upon completion of the install, at step (5) Installer 408 reports the status (success, failure, error messages, and so forth) back to the Change Coordinator.

[0037]FIG. 5 illustrates a preferred way in which ordinary control of the system is performed. As login access to the Install Servers and Change Coordinators preferably is tightly controlled, normal operations are performed over an HTTPS connection to the CC process on one of the Change Coordinators. As all Change Coordinators may communicate with all other Change Coordinators, and all Install Servers may communicate with one Change Coordinator, control messages can easily propagate to where they are needed.

[0038]FIG. 6 illustrates how new machines (not yet running IR) are brought into the management system. A Change Coordinator 600 notes that it has not heard from a given field machine 602 in an unacceptably long period of time and, at step (1), directs an Install Server 604 to make sure that the given host is brought up-to-date if possible. The Installer 606 queues that install and, at step (2), the Installer installs the field machine 602. Upon completion of the install, at step (3), the Installer reports the status (success, failure, error messages, and so forth) back to the Change Coordinator.

[0039] Change Coordinator Component Design

[0040] As noted above, the CC component is the primary controller for the larger set of components making up the full software management system. The main roles of this component include: performing as the communications hub of the whole software management system, driving a scheduling engine for determining the eligibility for installation of field machines, maintaining tables in a distributed data store, providing the interface to that data store for other system components, publishing install-related information into a distributed query mechanism for network-monitoring purposes, and maintaining network communications with other CC hosts to provide a reliable distributed core for the software management system.

[0041] As seen in FIG. 7, the CC component 700 preferably has multiple subsystems comprising: an external UI 702, a communication subsystem 704 for talking to Install Servers and other Change Coordinators, a reader mechanism 706 for acquiring data from IL, a mechanism 708 for publishing data for distributed data collection, a scheduling engine 710, and a data store interface 712. Each of these components is described below.

[0042] External UI

[0043] The user interface preferably has multiple layers, usable at any layer by an appropriately authorized user. A user logged in to the CC host may use command line tools locally to directly affect the CC's behavior. Instead, appropriate remote access mechanisms may be used to enable a properly authorized user to drive the CC command line from a remote location. The graphical UI is a wrapper around these tools, providing the primary and suggested interface for all common operations. This will be the means by which all normal control of the system is performed. Information passing through this interface, for example, may include: issuing commands to start installing a new release, issuing commands to pause, stop, or resume all installs, submitting information about the parameters of a new release, verifying a release's readiness for a given release phase, or issuing commands to modify operational configuration of the system.

[0044] Communication Subsystem for Talking to Installers

[0045] Each active Change Coordinator preferably maintains an open communication channel with at least one Installer. The protocol used between hosts/components in this situation is the Change Coordinator Control Protocol (CCCP). CCCP preferably uses a secured, encrypted TCP connection for transport, and it provides a simple remote object access protocol with an XML-RPC style of encoding. This protocol may also be used to enable Change Coordinators to talk to each other, for example, to detect network partitions, to synchronize databases, and to elect a leader.

[0046] IL Communication Subsystem

[0047] The output mechanism and locking protocol by which data gets from IL to the CC component is documented below. Preferably, this data will be read in continuously and used to update the CC's backend data store.

[0048] Publisher Mechanism

[0049] To facilitate monitoring and management, the CC will publish data into a distributed query mechanism.

[0050] Scheduling Engine

[0051] This engine is used to determine: which hosts are out of date and should be installed; and which hosts are safe to install (or possibly suspend) at any given moment, taking into given criteria, e.g., region bandwidth, machine interdependencies, suspend states, and the like. Several factors may go into these decisions, including several hard-coded rules in addition to the information presented to the CC via the external UI.

[0052] The scheduling engine typically will do its work by processing data in the shared database. When possible, it is preferable that rules are static, but some rules may also rely on changing near-real-time data. Preferably, there are two parts to each rule: content and description. The content of a rule is the list (or lists) of IP addresses that to which the rule applies. This content defines the set to which the rule applies. These lists may be generated statically from a configuration file that describes the install. This approach may not be sufficient for all rules, and are working on a means to generate the content dynamically from the distributed query system and perhaps other sources as well.

[0053] The description of a rule preferably takes one of the following three forms: no more than N (or N %) of the hosts in this set may be installed at one time; none of the hosts in this set may be installed until all of the hosts in some arbitrary other set are installed; none of the hosts in this set may be installed until a specific internal flag has been set.

[0054] A preferred algorithm used for scheduling and satisfying the rules is detailed in the following section.

[0055] Preferably, the scheduling engine internally publishes the hosts that have been determined to need an install and that are safe to install at the current time. The install-driving module of the CC will be the client of this information, taking machines from this pool whenever installation resources are available. Further details of this process are now described.

[0056] The scheduling algorithm is designed to accommodate that different hosts in the distributed network environment may have different functions or interdependencies, or that it may not be desirable to do installs on all hosts (or even a subset) at a given time. Thus, for example, certain hosts may be critical to the operation of other hosts, or to the distributed network as a whole and, thus, the scheduling algorithm must be flexible, yet still robust. According to the present invention, it is assumed that there are a plurality of hosts that need installs, but that given hosts are associated with one or more potentially overlapping constraint sets and/or have given precedent relationships. A “constraint set” (sometimes called a “rule”) will be created when any group of hosts are interdependent (typically in a direct manner) or where any group of hosts provides necessary redundancy (e.g., for safety purposes). There may be other constraint sets defined. A “precedent relationship” as the name applies is where particular host(s) must be installed before other hosts, e.g., to ensure proper system operation, process continuity, or the like. The scheduling algorithm preferably takes constraint set(s) and precedent relationships (if any) into consideration as follows.

[0057] Initially, the algorithm generates a first rank order of the hosts by assigning to each host a cumulative value of all constraint sets in which that host is contained. Then, the algorithm alters the first rank order to accommodate precedent relationships, if any, to generate a second rank ordering of the hosts. If there are no precedent relationships, the second rank order is the same as the first rank order. After the second rank order is generated, the scheduling algorithm implements a given heuristic. Thus, in a representative embodiment, the given heuristic assigns hosts into a set of one or more timeslots in a greedy fashion, i.e., pull hosts off the second rank ordering and continue pushing them into timeslot t₁ until a given constraint is violated, then continue with timeslot t₂, and so on.

[0058] In a given operating environment, the scheduling algorithm is run in a production mode, such that when timeslot 1 is filled, the routine stops. Thus, in this mode, given the current database (the install state of all hosts, viz., the field machines) and given the set of current rules (constraints), the algorithm returns the set of field machines that it is safe to execute a control action against at this particular time (i.e., at a given point in time or at points in time during the timeslot). At this point, the change coordinator instructs the install servers to install the hosts that have been pushed into the timeslot. In an alternative, the heuristic continues to assign hosts into more than one timeslot, which is useful as a “simulation” mode for testing purposes or the like. Thus, in the simulation mode, and given the same inputs, the output provides a grouped ordering (do group one at time 1, then group two at time 2, etc.) of all field machines on which to execute the control action.

[0059] The technique of assigning hosts into a set of one or more timeslots in a greedy fashion based on some rank ordering of the hosts is a variant of a graph coloring heuristic. As is known, multi-coloring a graph is an NP-complete problem that attempts to define a minimum number of colors for the nodes of a graph where no adjacent nodes are assigned the same color. According to the present invention, the scheduling algorithm heuristic considers the hosts as “nodes” and the timeslots as “colors.” A constraint set defines a subgraph, where all nodes contained in the particular subgraph have edges connecting them to all other nodes contained in that subgraph.

[0060] Scheduling Algorithm

[0061] The following is a representative and simplified description.

[0062] According to the algorithm, assign each host in the whole set a rank, as follows:

[0063] for each host:

[0064] rank is initialized to 0

[0065] for each constraint set that this host is in

[0066] X=size of constraint set/number allowed at once in set

[0067] rank=rank+X

[0068] for each host (some hosts may have non-zero rank):

[0069] for each host with a phost (a prior host) that must precede it due to some rule

[0070] (first, finish ranking for phost)

[0071] Y=rank of phost

[0072] rank=max(rank, (Y+1))

[0073] The first loop creates the first rank order, and the second loop alters the first rank order to create the second rank order. The first rank order output from the first loop is then applied as the input to the second processing loop. At the end of these steps, each host has a rank that roughly reflects how “constrained” that host is, and also how constraining that host is to other hosts.

[0074] The routine then sorts all hosts in descending rank order. Then, iterate over the hosts in this sorted order, finding timeslots (beginning at 0) for each host.

[0075] For a given host find the timeslot as follows:

[0076] 1. slot=EARLIEST[host] (this is initialized to 0 for all hosts before beginning)

[0077] 2. for each constraint set that host is in

[0078] if that constraint is already “full” for this time slot:

[0079] slot=slot+1

[0080] goto step 2

[0081] 3. slot value is now correct, set

[0082] 4. for each fhost that follows this host in a precedence rule

[0083] EARLIEST[fhost]=slot+1

[0084] Once this process has been completed for all hosts, the schedule is set.

[0085] To use this algorithm in a continuous fashion instead of lock-step scheduling, it is run frequently, with the results then simplified into two categories:

[0086] 1. In slot 0: can be started now

[0087] 2. In any other slot: cannot be started now

[0088] In other words, by simply ignoring all distinctions other than whether a host would currently be in slot 0, the routine effectively asks at any given time “which hosts are safe to start right now?”

[0089] Concrete Rules, Results, and Performance

[0090] If a rule is specified as “no more than N % of a set at once”, preferably this constraint is rounded down unless it would round to 0, in which case it will be rounded to 1.

[0091] The following are representative human-readable rules that may be used to define constraint sets:

[0092] No more than 1 host in a size 5 session agreement set at once.

[0093] No more than 20% of the hosts in the entire release at once.

[0094] No more than 20% of the edge servers at once.

[0095] Illustrative source code for the scheduling algorithm is set forth below (© 2002 Akamai Technologies, Inc.): import string import string # goal: produce a scheduling order of hosts that maintains all # given constraints class RuleInfo: def _init_(self, rfn, rifn): # rfn is the name of a “rules” file, the human-written file describing # constraints (format documented in rule_reader.pl) # rifn is the name of the rule_ips file, pregenerated from the rules # file and a network configuration file # some abbreviations used here: # rulename: the unique identifier for a given type of constraint # (specified in the rules and rule_ips files) # gid: the unique identifier for a specific set applied to by # some constraint # (arbitrary integer, determined internally) self. _lastgid = −1 # just a counter for generating gids self.noderanks = { } # keys are ip addresses, values are the rank of the node self.node_precedes = { } # ip addresses -> lists of ips that must precede the key self.node_follows = { } # ip addresses -> lists of ips that must follow the key self.bottoms = { } # ip addresses, if present and val is 1, then at end of prec chain self.node_g_memberships = { } # keys are ip addresses, values are lists of gids denoting # constraint sets that those ips belong in self.g_sizes = { } # keys are gids, values are the sizes of the constraint sets self.g_rates = { } # keys are gids, values are the most at once allowed in that group # the following two dicts are mostly just as intermediates for # generating some of the above self.ri_info = { } # rulename -> list of lists of ips self.r_info = { } # rulename -> cond_string # first, read the rule_ips file, get the full list of ips # and the list of lists of ips for each rule rifd = open(rifn) ri_lines = rifd.readlines( ) for line in ri_lines: tokens = string.split(line) rulename, data = tokens[0], tokens[1:] if rulename == “all_hosts”: # magic allips rule for ip in data: self.noderanks[ip] = 0 self.node_g_memberships[ip] = [ ] else: self.ri_info[rulename] = self._pound_break(data) rifd.close( ) # now we have all of the ips # read the rules file in order to get the constraint data rfd = open(rfn) for line in rfd: tokens = string.split(line) self.r_info[tokens[0]] = tokens[−1] rfd.close( ) for rulename, iplists in self.ri_info.items( ): for iplist in iplists: gid = self._nextgid( ) self.g_sizes[gid] = len(iplist) self.g_rates[gid] = self._get_rate(rulename, iplist) precs = self._get_precedents(rulename) cur_prec = self.node_precedes.keys( ) for ip in iplist: self.node_g_memberships[ip].append(gid) if ip not in cur_prec: self.bottoms[ip] = 1 for pip in precs: curprecs = self.node_precedes.get(ip, [ ]) curprecs.append(pip) self.node_precedes[ip] = curprecs curfollow = self.node_follows.get(pip, [ ]) curfollow.append(ip) self.node_follows[pip] = curfollow self.bottoms[pip] = 0 # now we have all constraint rates, memberships, and precedences # ready to start ranking! # we will order all IPs in descending order by the number of # constraint sets that they are present in (roughly) # this will cause us to try to schedule the most constrained IPs first for node in self.noderanks.keys( ): con = 0 for gid in self.node_g_memberships[node]: con = con + (self.g_sizes[gid]/self.g_rates[gid]) + 1 # the bigger the set (or slower the rate) the more # constraining it is... self.noderanks[node] = con # now we have the ranking purely by set memberships # modify to take precedence into account for node in self.noderanks.keys( ): self._fix_rank_precedence(node) # now we have our final rankings # produce a flat sorted list of ips from the rankings val_d = { } for val in self.noderanks.values( ): val_d[val] = [ ] for ip, con in self.noderanks.items( ): val_d[con].append(ip) vals = val_d.keys( ) vals.sort( ) vals.reverse( ) self.sorted_ips = [ ] for val in vals: for ip in val_d[val]: self.sorted_ips.append(ip) # we now have our ordered list of IPs # put them in the schedule self.schedule( ) # we now have a list of lists of ips in self.result # these are our ordered steps for installation def schedule(self): # we should never take more steps to install than 1+highest_(—) rank maxsteps = 1+max(self.noderanks.values( )) scheduled = { } # int -> list of ips in that step (0-indexed) for i in range (maxsteps): scheduled[i] = [ ] # initialize to no ips scheduled setsched = { } # gid -> array of int of num scheduled at indexed step for gid in self.g_sizes.keys( ): setsched[gid] = _zeros(maxsteps) # nothing scheduled yet # earliest is used for precedence management earliest = { } # ip -> slot # ready, set, go. for ip in self.sorted_ips: slot = earliest.get(ip, 0) found = 0 while not found: # find the first time slot for which all applicable # constraint sets allow another host to be scheduled for constraint in self.node_g_memberships[ip]: capacity = self.g_rates[constraint] if setsched[constraint][slot] == capacity: # already full at this slot slot = slot + 1 break else: found = 1 # found our slot, do bookkeeping scheduled[slot].append(ip) for constraint in self.node_g_memberships[ip]: setsched[constraint][slot] = setsched[constraint][slot] + 1 for fnode in self.node_follows.get(ip, [ ]): earliest[fnode] = max(earliest.get(fnode, 0), slot+1) # done, now just cleanup and result formatting self.setsched = setsched self.result = [ ] steps = scheduled.keys( ) steps.sort( ) for step in steps: val = scheduled[step] if val: self.result.append(val) # finis def _get_precedents(self, rulename): # given a rulename and an already populated self.r_info, # return list of ips that must precede all ips in this rule res = [ ] cond = self.r_info[rulename] if cond[0] != “_”: # not a prec rule return res prec = cond[1:] if prec == “_”: # nop rule return res for iplist in self.ri_info[prec]: for ip in iplist: res.append(ip) return res def _get_rate(self, rulename, iplist): # given a rulename, list of ips in a set of that rule, # and a populated self.r_info, return the maximum number of # hosts in that iplist that may be scheduled at once size = len(iplist) cond = self.r_info[rulename] if cond[0] == “_”: # prec rule, max size return size cond_type, cond_val = cond[0], cond[1:] if cond_type == ‘n’: return int (cond_val) elif cond_type == ‘p’: return max(int((float(cond_val) / 100) * size), 1) else: raise “unknown condition value %s” % cond def _nextgid(self): # just a simple counter/generator self._lastgid = self._lastgid + 1 return self._lastgid def _pound_break(self, plist): # given a list of strings, some of which are “#”, # return a list of lists, breaking on the “#” items res = [ ] tmp = [ ] while plist: next, plist = plist[0], plist[1:] if next == ‘#’: if tmp: res.append(tmp) tmp = [ ] else: tmp.append(next) if tmp: res.append(tmp) return res def _fix_rank_precedence(self, node): # re-rank nodes from here upward on the precedence chain # in order to force preceding nodes to have higher ranks for fnode in self.node_follows.get(node, [ ]): self.noderanks[node] = max(self.noderanks[node], (self.noderanks[fnode]+1)) for pnode in self.node_precedes.get(node, [ ]): self._fix_rank_precedence(pnode) def _zeros(lenz): # because we stopped using Numeric, but still need this r = [ ] for i in range(lenz): r.append(0) return r def main(rfn, rifn): ri = RuleInfo(rfn, rifn) ln = [ ] for step in ri.result: ln.append(len(step)) print ln print len(ri.result) if _name_== ‘_main_’: import sys main(sys.argv[1], sys.argv[2])

[0096] Datastore Interface

[0097] The Change Coordinator also uses structured, embedded, fast, highly available storage. Data that should reside in this storage includes, but is not limited to: the parameters that can fully describe each release, and the state of hosts with regard to install status.

[0098] Installer Component Design Details

[0099] As noted above, the primary purposes of the Installer component include: installing software to field machines, and communications with the Change Coordinator (CC) component. The Installer component 800 preferably has three subsystems as illustrated in FIG. 8: Installer will maintain a thread pool 802, each member of which is capable of driving software installs to field machines; Installer will communicate with whichever Change Coordinator contacts it, using the communication subsystem 804 via Change Coordinator Communication Protocol (CCCP) over the secure, encrypted TCP connection (as has been described); and Installer will publish data to the query mechanism for monitoring purposes using a publishing mechanism 806.

[0100] The Installer preferably maintains and monitors the thread pool 802 and a queue 808. At the request of a Change Coordinator, a given IP/release pair will be inserted into the queue for installation. Whenever the thread pool is not at its maximum capacity and the queue is not empty, the next item will be removed from the queue and an installer thread will be created for it. The Installer preferably has resident on it all of the current software components that are contained in any valid release, as well as definitions of each of those releases. A means of securely and efficiently transferring the data and bundles to the Installer is assumed to exist. Installer threads 802 a-n perform the actual software installation using an application deployment routine optimized for this sort of usage model. Substantial detailed feedback about install status preferably is reported back into the main Installer program. The Installer shall also be able to run audits against machines after running installs to them. The output of the audits must be reported to the CC and possibly also directly into the query mechanism for alert-raising purposes. Preferably, configuration parameters such as the maximum number of concurrent install threads will be runtime-configurable without needing to restart the Installer program.

[0101] As noted above, the Installer interacts with the Change Coordinator. These components may communicate using a token-based wire protocol, although RPC is preferred. In particular, the communication may use an XML-RPC protocol over a secure, encrypted TCP socket. The communication content typically includes: instructions from CC to Installer for Installer configuration parameters, instructions from CC to Installer to install a given host to a given release; and feedback from Installer to CC on install progress/success/failure/failure-reasons.

[0102] Install Reporter (IR) and Install Listener (IL) Subcomponent Design

[0103] The primary purpose of this pair of components is to provide reporting of host install states to the Change Coordinators. The two components taken together may be seen as one system. The basic design is as follows: the IL listens on given UDP and TCP ports on chosen servers; the IR runs regularly and briefly on every field machine; when invoked, the IR sends a message to an arbitrarily-chosen host that is running IL; and the IL receiving the message outputs the message for use by the Change Controller. Communication between the two components preferably is one-way; an IR only sends messages, and an IL only receives them.

[0104] The IR component preferably is frequently invoked and short-lived. It reads a configuration file to gain the following information: protocol version being used (this may be hard-coded instead), and DNS hostname to which datagrams are sent. When invoked, the following sequence occurs: a first configuration file is read for configuration information, a second configuration file is read for data content information, IR decides randomly whether to use TCP or UDP, a datagram is sent to the IL hostname read from the first configuration file, and the component exits with an exit status of 0.

[0105] The IL component runs in a fairly standard model. It is preferably long-lived and runs on arbitrary field hosts. To keep the data transfer model simple, however, preferably IL runs on CC hosts. This component is constantly bound to given UDP and TCP ports. A simplified version of this component writes its output to files in a given directory, although more sophisticated means of communication may be used. Upon receiving a datagram from a host running IR, the data is presented into the current output method. This component provide data into the query mechanism. The following may be published: approximate number of reports received per minute, and amount of time since last output file rotation.

[0106] The Change Coordinator is responsible for the receiving half of the following output method, and for interpreting the body of the IR reports. Some information should probably be published to the query mechanism about this data by the CC, such as: datagrams received where the apparent source IP differs from the IP in the body; datagrams received where the content is ill-formed; and datagrams being received with an unknown protocol version.

[0107] Applications

[0108] One distributed computing environment in which the present invention may be implemented is a content delivery network (CDN). It is known to deliver digital content (e.g., HTTP content, streaming media and applications) using an Internet content delivery network (CDN). A CDN is a network of geographically distributed content delivery nodes that are arranged for efficient delivery of content on behalf of third party content providers. Typically, a CDN is implemented as a combination of a content delivery infrastructure, a request-routing mechanism (preferably based in DNS), and a distribution infrastructure. The content delivery infrastructure usually comprises a set of “surrogate” origin servers that are located at strategic locations (e.g., Internet network access points, Internet Points of Presence, and the like) for delivering content to requesting end users. The request-routing mechanism allocates servers in the content delivery infrastructure to requesting clients in a way that, for web content delivery, minimizes a given client's response time and, for streaming media delivery, provides for the highest quality. The distribution infrastructure consists of on-demand or push-based mechanisms that move content from the origin server to the surrogates. An effective CDN serves frequently accessed content from a surrogate that is optimal for a given requesting client. In a typical CDN, a single service provider operates the request-routers, the surrogates, and the content distributors. In addition, that service provider establishes business relationships with content publishers and acts on behalf of their origin server sites to provide a distributed delivery system.

[0109] More generally, the present invention is useful in any distributed networking environment in which it is required to install software on field machines that are interdependent and/or that provide redundancy to each other. Typically, field machines are associated with one or more constraint sets, as has been previously described.

[0110] Variants

[0111] A skilled artisan will appreciate that the Install Reporter and Install Listener components may be omitted without impacting the basic functionality of the system. The Change Coordinator database stores the known install status of every field machine and a last time that the status was verified or known. When the IR and IL routines are omitted, the Change Coordinator status database can be populated in other ways, e.g., by having an Install Server simply report back each successful installation (which information may be provided anyway). The IR routine provides an optimization to provide the system with information that it might not otherwise obtain, namely, that a particular machine is out-of-date. This is particularly important in the case where the field machine has been disconnected from the network for a long time period. 

Having described my invention, what I claim is as follows:
 1. A system for managing installs to a set of one or more field machines in a distributed network environment, comprising: at least one change coordinator server that includes a database with data identifying a current state of each field machine, and a change controller routine for initiating a given control action to initiate an update to the current state on a given field machine; and at least one install server responsive to the change controller routine initiating the given control action for invoking the update to the current state on the given field machine.
 2. The system as described in claim 1 wherein the change controller routine includes a scheduling algorithm that evaluates data from the database and identifies a set of field machines against which the given control action may be safely executed at a given time.
 3. The system as described in claim 2 wherein the scheduling algorithm implements a given heuristic.
 4. The system as described in claim 2 wherein the given heuristic assigns a rank ordered set of field machines to a set of one or more timeslots.
 5. The system as described in claim 1 further including an install reporter routine that executes on the given field machine for providing the change controller server with information on the current state of the given field machine.
 6. The system as described in claim 5 wherein the information identifies a given software release and an IP address of the given field machine.
 7. The system as described in claim 1 wherein the install server invokes installation using an application deployment utility.
 8. The system as described in claim 5 wherein field machines are servers of a content delivery network (CDN).
 9. Apparatus for managing installs to a set of hosts, wherein the installs are invoked from a set of one or more install servers, the apparatus comprising: a database of install states of the set of hosts; and a change controller routine for using data from the database and initiating a given control action to a given one of the install servers to initiate an install on one or more given hosts.
 10. The apparatus as described in claim 9 wherein the change controller routine evaluates install state data from the database and identifies a subset of the hosts against which the given control action may be safely executed at a given time.
 11. The apparatus as described in claim 10 wherein the change controller routine implements a given heuristic.
 12. The apparatus as described in claim 11 wherein the given heuristic assigns a rank ordered set of hosts to a set of one or more timeslots.
 13. A system for managing installs to a set of one or more field machines, comprising: a set of change coordinator servers, wherein each change coordinator server includes a database, an install listener routine that receives reports from install reporter routines running on the given field machines and populates the database with data identifying the given software release running on the field machines, and a change controller routine for initiating a given control action to initiate an install on a given field machine, wherein the given control action is initiated if the given field machine requires an install of a new software release; and a set of install servers, wherein each install server is responsive to a change controller routine in a given change coordinator server initiating the given control action for invoking installation of the new software release on a given field machine.
 14. The system as described in claim 13 wherein each change coordinator server also includes code for synchronizing its database with the databases in other change coordinator servers.
 15. The system as described in claim 13 wherein each of the set of install servers has the capability of communicating with a given change coordinator server to enable the given change coordinator server to manage installs for the set of install servers.
 16. The system as described in claim 13 wherein a given change coordinator routine includes a rules-based scheduling engine that evaluates data from the database against at least one rule to determine which field machines are eligible for installation at a given time. 